The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 11, 2026 4:40pm

PR Summary

High Risk
Touches security-critical authorization paths for OAuth credentials, file downloads, and human-in-the-loop resume/cancel flows; mistakes could block legitimate access or leave residual IDOR exposure.

Overview
Closes multiple cross-tenant IDOR vectors by standardizing API routes on authorizeCredentialUse for OAuth credential usage (Gmail/OneDrive/Outlook/Wealthbox selectors, Wealthbox OAuth item route, and Vertex credential resolution in providers).

Hardens file transfer by verifying the caller owns the referenced storage key (verifyFileAccess) before WordPress uploads download from storage.

Scopes human-in-the-loop pause/resume/cancellation operations by requiring workflowId in PauseResumeManager lookups and propagating it through resume, poll, and cancel endpoints, plus more consistent error handling via toError.

^{Reviewed by Cursor Bugbot for commit 026405f. Configure here.}

Greptile Summary

This PR closes a suite of cross-tenant IDOR vulnerabilities by replacing ad-hoc resolveOAuthAccountId + conditional workspace-permission checks with the unified authorizeCredentialUse gate, adding workflowId scoping to all PauseResumeManager methods (preventing unauthorized cancel/resume of another tenant's paused execution), and adding verifyFileAccess ownership verification to the WordPress upload route.

• OAuth credential IDOR (6 routes): Routes for Gmail labels, OneDrive files/folders, Outlook folders, Wealthbox items (×2), and Vertex AI now call authorizeCredentialUse, which enforces ownership on every credential type including the legacy account-ID fallback path that previously silently skipped all ownership validation.
• HITL IDOR: All PauseResumeManager cancellation/resume methods now require a workflowId and scope their database lookups with AND workflow_id = ?, closing the gap where any authenticated user could cancel or resume another tenant's paused workflow.
• File ownership: The WordPress upload route now hard-fails with 404 when the acting user is not an owner of the supplied S3 key.

Confidence Score: 5/5

Safe to merge — all cross-tenant credential and execution-control gaps are consistently closed with no behavioral regressions found.

All three fix categories (OAuth credential IDOR, HITL cancel/resume IDOR, WordPress file ownership) are correctly and completely implemented. Previously flagged concerns about processQueuedResumes, getPausedCancellationStatus, and completePausedCancellation missing workflowId are fully addressed. The authorizeCredentialUse refactor removes dead actingUserId guards without changing observable behavior.

No files require special attention — the core security logic in credential-access.ts and human-in-the-loop-manager.ts was reviewed thoroughly and is correct.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Client
    participant ToolRoute as Tool Route (gmail, onedrive, etc.)
    participant ACA as authorizeCredentialUse
    participant DB as Database
    participant OAuthUtils as refreshAccessTokenIfNeeded

    Client->>ToolRoute: "GET /api/tools/... ?credentialId=X"
    ToolRoute->>ACA: "authorizeCredentialUse(request, {credentialId})"
    ACA->>DB: checkSessionOrInternalAuth
    ACA->>DB: "SELECT FROM credential WHERE id = credentialId"
    alt Platform credential (OAuth/SA)
        ACA->>DB: SELECT FROM credential_member WHERE credentialId AND userId
        ACA->>DB: getUserEntityPermissions(actingUser, workspace)
        ACA-->>ToolRoute: ok: true, credentialOwnerUserId
    else Legacy account ID
        ACA->>DB: "SELECT FROM account WHERE id = credentialId"
        ACA->>ACA: "auth.userId === account.userId?"
        ACA-->>ToolRoute: ok: true, credentialOwnerUserId
    end
    ToolRoute->>OAuthUtils: refreshAccessTokenIfNeeded(credentialId, ownerUserId)
    OAuthUtils-->>ToolRoute: accessToken
    ToolRoute-->>Client: 200 with data

_{Reviews (6): Last reviewed commit: "fix(security): harden workflowId scoping..." | Re-trigger Greptile}

@cursor review

@greptile

Follow-up fix (fd234ac): threaded workflowId through the remaining 4 processQueuedResumes call sites in human-in-the-loop-manager.ts that were still missing it — persistPauseResult (line 267), startResumeExecution success path (line 507), startResumeExecution error path (line 535), and clearPausedCancellationIntent (line 1692). In all cases workflowId was already in scope; this just wires it through to the existing optional parameter. All 4 call sites now pass tenant scope — no remaining gaps.

Quality pass complete (0d4c9c6):

• catch (error: any) → catch (error) + toError(error).message in both the resume route and cancel route — no more type escape hatch on caught errors
• WordPress upload: removed 4 what-not-why inline comments (Process file, Use provided filename, Upload to WordPress using multipart, Add optional metadata)
• OneDrive files: collapsed the debug item-breakdown reduce+log and the file-IDs log into a single structured info log; consolidated the URL-branch comments into one truthful line; simplified the .filter() call
• HITL manager (updateSnapshotAfterResume): removed 3 redundant DAG-edge comments

All 4 original review threads were already resolved before this pass. Lint is clean.

@cursor review

@greptile

@cursor review

@greptile

@greptile

@cursor review

@greptile

@cursor review